Help ! - getting this error in setup. Failed to compile MOF C:\Program Files\Microsoft Configuration Manager\bin\i386\smsRprt.mof, error -2147217407 The client is using Remote SQL with a named instance. I've seen these articles http://www.eggheadcafe.com/software/aspnet/31663918/compilemoffile-failed-to.aspx and http://myitforum.com/cs2/blogs/jgilbert/archive/2007/10/11/using-sql-server-named-instances-to-host-the-configuration-manager-site-database.aspx I have run setspn using both the FQDN for mssqlsvc and the instance name but still getting failure of setup Any thoughts ? Thanks

Sometimes I've had success by restarting the SQL Server machine for this error. Our troubleshooting topic can be found here: http://technet.microsoft.com/en-us/library/bb932163.aspx

Thanks for the reply Jeff Could I just clarify the setspn command required. Is it Setspn -A MSSQLSvc/<SQL Server name>:1433 <domain>\<user> OR Setspn -A INSTANCESERVICENAME/<SQL Server name>:1433 <domain>\<user> where instanceservicename is the name of the service that runs the SQL instance? At the moment I have 4 SPN entries comprising the MSSQLSVc + FQDN and the instanceservicename as described I didn't reboot the server but will give it a try on Monday

Bump - anybody ? I'm trying to understand what the MSSQLSvc refers to i.e. is it the service name under which SQL is running and therefore whether it changes if the service name is different as with a different instance name OR whether its simply the server and port that is doing the verifying?

Hi, The command is: setspn MSSQLSvc/SQLSERVER1.contoso.com:1433

Well its a strange one, but the client had setup remote SQL server as an instance name (not with the default). They said it would always "listen" on port 1433. In the end I went into SQL config mgr and set the TCP ports from blank (which they said would mean the default) to 1400. I then recreate the setspn commands for netbios and fqdn under 1400 and the setup worked correctly - happily ! I'm still confused why 1433 wouldn't work when they were definitely set up for the named service account

I got the same error, sms provider failed to install and the log shows unable to compile smsRprt.mof.I did some research on this problem for several days and foundfollowing articles might be helpful:How to use Kerberos authentication in SQL ServerHow to Configure an SPN for SQL Server Site Database ServersTroubleshooting Configuration Manager SetupSo I have following actions taken:- Use setspn -x to checkduplicated SPNs and removed the corrutpted items- Use setspn -a MSSQLSvc/<NETBIOS-name>:1433 domain\sql-account and setspn -a MSSQLSvc/<FQDN>:1433 domain\sql-account to register SPN, do remember you need both of them- Add the domain account for running SQL service to the Administrators group ofsite dbserver(I know it's stupid but the troubleshooting article asked to do so)- Modify the property of site server computer account, enable trust for delegate by ADU&C- Modify the property of SQL service account, enable trust for delegate by ADU&CFortunately, I finally successfully completed ConfigMgr 2007 setup. (Maybe there's extra useless action, I'll prove them later.)BTW, many google search results said that you need to use setspn -a MSSQLSERVER/<computer-name>:1433 domain\account instead of MSSQLSvc. I didn't see any Microsoft official article to use that string. Don't be mislead.

Hi, sms provider failed during the installation phase (install sms provider) of primary site with database not localy present in this server. I tried all actions written above but with always the same result : sms provider installation failed. i renamed my server and i tried again to install my site server but this time SMS provider was successfully installed. Installation of this primary site was successfully completed

I had this same issue today and found out I had a unique scituation and solution and thought I would share it. I had changed the default name to one of the SCCM reports. It happened to be the very first report "Computer information for a specific computer". It's a long story why I changed the name so I will spare you as it's not relevent. All I did was append "custom" to the name. Any way, if you look at the smsrprt.mof, it has the queries, report ID, etc information. So I am guessing it queries WMI for these properties and it couldn't find it. Basically I just renamed the default report back to it's original name and that resolved my issue.

There's also a KB published on this error just this week http://support.microsoft.com/default.aspx?scid=kb;en-us;2384060&sd=rss&spid=12769 John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|